Windows Connection Manager

The Windows Connection Manager enables you to scan hundreds of nodes Agentlessly using WinRM and remote PowerShell as the connection protocol. Essentially working as a connection proxy, the Windows Connection Manager provides a single point of management for all configuration, logging, and updating of nodes. If you opt for the Agentless scanning of your nodes via the Windows Connection Manager, there are two methods available for installation, see Installation Methods below for more information.

Agentless Scanning

In contrast to Agent-based scanning, the Windows Connection Manager can be deployed remotely and scan hundreds of nodes per Connection Manager. Once deployed, the Connection Manager polls the Guardian appliance every few seconds to check if there are any tasks to complete. Depending on the amount of nodes in your environment, your Guardian Representative can assist with capacity planning to ensure you have the correct amount of Connection Managers required for scanning.

Each Connection Manager is assigned to a Connection Manager group. Connection Manager groups should only contain Connection Managers of the same type; Windows or Linux. Target nodes are then assigned to Connection Manager groups, to ensure that they are being scanned via the correct connection protocol. For more information about Connection Manager groups, see Connection Manager Groups.

Installation Methods

Cloudhouse offer two methods for installing the Windows Connection Manager. Depending on whether you'd prefer to complete the installation using the Windows UI, or automate it via a script, you may prefer to opt for one deployment solution over the other. However, the scan results for both methods are the same.

A Windows Connection Manager can be installed via one of the following methods:

• Windows Installer – The Connection Manager is downloaded and installed via the Cloudhouse Guardian Connection Manager installer. You are required to register the Connection Manager to the Guardian appliance and configure it to run as a Windows service user. For more information, see Windows Connection Manager – Installer.

• Command Line – The Connection Manager is downloaded and installed via Command Line. You are required to register the Connection Manager to the Guardian appliance and configure it to run as a Windows service user. For more information, see Windows Connection Manager – Command Line Installation.

Note: Cloudhouse also offer flexible customizations of your Connection Manager's configuration to aid your deployment. For more information, see Agents and Connection Managers – Configuration.

Once you have decided on the installation method for your Connection Manager, you can host it within your private network. This method requires no Internet access for your target nodes to be scanned.

Windows Domains

Windows Only

To ease with setup and node scanning, it is highly recommended that a Windows Connection Manager is installed and registered with the Guardian appliance for each domain in your environment. These Connection Managers can be a part of the same Connection Manager group or different groups corresponding to the different domains in your environment.

Note: Connection Managers attempting to issue WinRM requests to machines in a different domain will need to have a TrustedHosts rule configured.